Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de1fe32724a2ecaede04bcc2c8c1ca11a5ea7f6af374a463d6a2d33ce225db7a

Tx prefix hash: f36d44595f5878ef5c558d95b3b09c3458be3dade16f3166b074e51565a5453c
Tx public key: 3319ebe625f6d6ceef100c57a088a820fe992329f70903639087aaf4ca0e82ae
Timestamp: 1759026951 Timestamp [UCT]: 2025-09-28 02:35:51 Age [y:d:h:m:s]: 00:117:05:08:48
Block: 1377987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83798 RingCT/type: yes/0
Extra: 013319ebe625f6d6ceef100c57a088a820fe992329f70903639087aaf4ca0e82ae021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4905ae0cef71a615309d1f257c52ae4b28a32c6643b4792b1e28cae06dc2e3bb 0.600000000000 1866082 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": 1377997, "vin": [ { "gen": { "height": 1377987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4905ae0cef71a615309d1f257c52ae4b28a32c6643b4792b1e28cae06dc2e3bb" } } ], "extra": [ 1, 51, 25, 235, 230, 37, 246, 214, 206, 239, 16, 12, 87, 160, 136, 168, 32, 254, 153, 35, 41, 247, 9, 3, 99, 144, 135, 170, 244, 202, 14, 130, 174, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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