Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be97d43b8ad2df3fb393933a41518e707f6d9f81c48601e6f432102632021421

Tx prefix hash: 0dfcca95c19e51c44757be752222c05be48e5b0b979bb5d3804934f4813b8ddf
Tx public key: 9e8d1c85a6cd28fd26b95bae467deaa45a535c289470e5f9a71467223c2c17a9
Timestamp: 1760784028 Timestamp [UCT]: 2025-10-18 10:40:28 Age [y:d:h:m:s]: 00:083:06:53:02
Block: 1392564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59629 RingCT/type: yes/0
Extra: 019e8d1c85a6cd28fd26b95bae467deaa45a535c289470e5f9a71467223c2c17a902110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 356deb5315adff294e4efed0171cf467ea49612a05f07f208c01e4c9359b7291 0.600000000000 1880815 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": 1392574, "vin": [ { "gen": { "height": 1392564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "356deb5315adff294e4efed0171cf467ea49612a05f07f208c01e4c9359b7291" } } ], "extra": [ 1, 158, 141, 28, 133, 166, 205, 40, 253, 38, 185, 91, 174, 70, 125, 234, 164, 90, 83, 92, 40, 148, 112, 229, 249, 167, 20, 103, 34, 60, 44, 23, 169, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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