Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84620920f60ce17f3c96e21e7b1e91b01b70627bd7daf4cc2ef02f22d2decdb4

Tx prefix hash: 0dc699e6e6cb953453522963a9cf27f95dc2888dcd8d66acaeb05395aab9a013
Tx public key: 5fbf991e0537d988e34f4dd01c849507d712be3b6f34b929625fe6792a2f0f27
Timestamp: 1737752374 Timestamp [UCT]: 2025-01-24 20:59:34 Age [y:d:h:m:s]: 00:144:06:15:12
Block: 1204529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102851 RingCT/type: yes/0
Extra: 015fbf991e0537d988e34f4dd01c849507d712be3b6f34b929625fe6792a2f0f27021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b26f67fc39e2662bf0d18e8c7fa2dd132548bcefe917d409ad32fe89c6f5edb 0.600000000000 1691216 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": 1204539, "vin": [ { "gen": { "height": 1204529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b26f67fc39e2662bf0d18e8c7fa2dd132548bcefe917d409ad32fe89c6f5edb" } } ], "extra": [ 1, 95, 191, 153, 30, 5, 55, 217, 136, 227, 79, 77, 208, 28, 132, 149, 7, 215, 18, 190, 59, 111, 52, 185, 41, 98, 95, 230, 121, 42, 47, 15, 39, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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