Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 425302a6395854972f7aca3533b3dcc28d3892c33ed394e96f4ffec6d7084dc6

Tx prefix hash: 0efec161c7c0d2e1c444fb98227a7fed53db00918614a2e2d827a8255c476d42
Tx public key: 377fc67a0c56a788e6720b9bc35a5e2d24baae902e14c92d7a1ba27aea924824
Timestamp: 1740819459 Timestamp [UCT]: 2025-03-01 08:57:39 Age [y:d:h:m:s]: 00:265:15:23:56
Block: 1229694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187610 RingCT/type: yes/0
Extra: 01377fc67a0c56a788e6720b9bc35a5e2d24baae902e14c92d7a1ba27aea9248240211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9fe2b569587af0146cd00d6309ca8aade3086c6c465a54713a4f479c2acee87 0.600000000000 1716581 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": 1229704, "vin": [ { "gen": { "height": 1229694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9fe2b569587af0146cd00d6309ca8aade3086c6c465a54713a4f479c2acee87" } } ], "extra": [ 1, 55, 127, 198, 122, 12, 86, 167, 136, 230, 114, 11, 155, 195, 90, 94, 45, 36, 186, 174, 144, 46, 20, 201, 45, 122, 27, 162, 122, 234, 146, 72, 36, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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