Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf5d0060428429f5007a1bc6f7a5e4d8df97df7bfc51cba5f94c609f0493b044

Tx prefix hash: 31875a6c5b3821b9b4343258f39944b1b40a2d2fc91ee11deaefff4369c23701
Tx public key: cb2e28c96fa5d19206fc37aaef77f1dd9fddcdd1a1c88affd14b4fb65f9aaecf
Timestamp: 1715463625 Timestamp [UCT]: 2024-05-11 21:40:25 Age [y:d:h:m:s]: 00:291:06:43:38
Block: 1019975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208144 RingCT/type: yes/0
Extra: 01cb2e28c96fa5d19206fc37aaef77f1dd9fddcdd1a1c88affd14b4fb65f9aaecf02110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6621b53cd2b8a94609ef410b3c71a064399fab77ab98e3def7da900cc0c23cf 0.600000000000 1484034 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": 1019985, "vin": [ { "gen": { "height": 1019975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6621b53cd2b8a94609ef410b3c71a064399fab77ab98e3def7da900cc0c23cf" } } ], "extra": [ 1, 203, 46, 40, 201, 111, 165, 209, 146, 6, 252, 55, 170, 239, 119, 241, 221, 159, 221, 205, 209, 161, 200, 138, 255, 209, 75, 79, 182, 95, 154, 174, 207, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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