Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34bb2fd914d2d75a49e1559e9043e91a2433135dc26f4822ccc8978a0794a90a

Tx prefix hash: e58068717b77123655ba0dc3441db3fe2b2c2ef1882171a9d1094abb60c0e219
Tx public key: 35aa80bf43796e15b5f93c0c0af4ae516d0f33f12740c08da1af4be818cbef92
Timestamp: 1761825309 Timestamp [UCT]: 2025-10-30 11:55:09 Age [y:d:h:m:s]: 00:009:15:57:58
Block: 1401197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6910 RingCT/type: yes/0
Extra: 0135aa80bf43796e15b5f93c0c0af4ae516d0f33f12740c08da1af4be818cbef92021100000003df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d5478636dd0ee25eec76d1e0e524f89566801e6e654dbb547564278f5f24552 0.600000000000 1889516 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": 1401207, "vin": [ { "gen": { "height": 1401197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d5478636dd0ee25eec76d1e0e524f89566801e6e654dbb547564278f5f24552" } } ], "extra": [ 1, 53, 170, 128, 191, 67, 121, 110, 21, 181, 249, 60, 12, 10, 244, 174, 81, 109, 15, 51, 241, 39, 64, 192, 141, 161, 175, 75, 232, 24, 203, 239, 146, 2, 17, 0, 0, 0, 3, 223, 90, 36, 122, 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