Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 431b33a4ebf3090ae1e2471bc1b9112e79b9129bc7e70e21aaffd86eefb9e546

Tx prefix hash: 6e660f75741462361b30a114fe132747ae5696b9d3211dfd89602206750d8d93
Tx public key: cbb71f5c89192053306c2090ed39a67e823e8ef38641ad99377a8dfb7cb2e2f2
Timestamp: 1766154478 Timestamp [UCT]: 2025-12-19 14:27:58 Age [y:d:h:m:s]: 00:002:08:12:27
Block: 1437069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1669 RingCT/type: yes/0
Extra: 01cbb71f5c89192053306c2090ed39a67e823e8ef38641ad99377a8dfb7cb2e2f2021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 902574b7afde701a7bd32867cabb8d1e5b1e93dba07e5fdc21bd0f7d7c89a81d 0.600000000000 1925874 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": 1437079, "vin": [ { "gen": { "height": 1437069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "902574b7afde701a7bd32867cabb8d1e5b1e93dba07e5fdc21bd0f7d7c89a81d" } } ], "extra": [ 1, 203, 183, 31, 92, 137, 25, 32, 83, 48, 108, 32, 144, 237, 57, 166, 126, 130, 62, 142, 243, 134, 65, 173, 153, 55, 122, 141, 251, 124, 178, 226, 242, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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