Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 00d0397db4012a0891de4787ab1bd782a703c3321e2ff3841c14d85e7837302f

Tx prefix hash: 7f9304fc19c868af6a2a2e0ee4c59b88242c092a342ef8c6c286ff1289a854e7
Tx public key: 8184527e68252ba9da0a3d67845b7ecbfc4a98a639100d5091d76b7ec917a189
Timestamp: 1726074100 Timestamp [UCT]: 2024-09-11 17:01:40 Age [y:d:h:m:s]: 00:253:18:45:15
Block: 1107910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181253 RingCT/type: yes/0
Extra: 018184527e68252ba9da0a3d67845b7ecbfc4a98a639100d5091d76b7ec917a18902110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08f243f33547ea957d28d66b46498780e74d4a1a9b0fc01b8aa47d60a65a856b 0.600000000000 1585621 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1107920, "vin": [ { "gen": { "height": 1107910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08f243f33547ea957d28d66b46498780e74d4a1a9b0fc01b8aa47d60a65a856b" } } ], "extra": [ 1, 129, 132, 82, 126, 104, 37, 43, 169, 218, 10, 61, 103, 132, 91, 126, 203, 252, 74, 152, 166, 57, 16, 13, 80, 145, 215, 107, 126, 201, 23, 161, 137, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8