Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e161487bfe42a51bed0b8965ce4ab400add9f06dc3ef83b2c17d069deff05940

Tx prefix hash: c447fcc62434f298261ef8c156cbd150af2e8545a8f25c8e04f0bc1942c3ddcb
Tx public key: 124ec986c35ce5246eabb3d7fbd85e1d59bfe3b19a9605ccf5fe786ec0fa0a4e
Timestamp: 1757436276 Timestamp [UCT]: 2025-09-09 16:44:36 Age [y:d:h:m:s]: 00:056:22:57:42
Block: 1364842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40748 RingCT/type: yes/0
Extra: 01124ec986c35ce5246eabb3d7fbd85e1d59bfe3b19a9605ccf5fe786ec0fa0a4e021100000015ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 756cdf761b7e03b2713794db7a8d1c09f40693186a7aa3a3a0c658c3311c94b6 0.600000000000 1852881 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": 1364852, "vin": [ { "gen": { "height": 1364842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "756cdf761b7e03b2713794db7a8d1c09f40693186a7aa3a3a0c658c3311c94b6" } } ], "extra": [ 1, 18, 78, 201, 134, 195, 92, 229, 36, 110, 171, 179, 215, 251, 216, 94, 29, 89, 191, 227, 177, 154, 150, 5, 204, 245, 254, 120, 110, 192, 250, 10, 78, 2, 17, 0, 0, 0, 21, 173, 121, 72, 208, 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