Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd61352f9f1616b11ca45f49f1197fc7a146756a2bf5aec716b806ab3c2546dc

Tx prefix hash: 399bf5dfcfcc60f471d96ac001687a296bb3ee7582ddd81ea31353e27245a69a
Tx public key: a7fd33e8b56c8e407c1c2af2fea7cf762267e668b55b025b8edab5a03b91cb86
Timestamp: 1737233784 Timestamp [UCT]: 2025-01-18 20:56:24 Age [y:d:h:m:s]: 00:150:05:10:23
Block: 1200253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107091 RingCT/type: yes/0
Extra: 01a7fd33e8b56c8e407c1c2af2fea7cf762267e668b55b025b8edab5a03b91cb860211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b0ea739bb4eccab4d58905eeaaf67795303552dba62f11014454f83907e5731 0.600000000000 1686896 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": 1200263, "vin": [ { "gen": { "height": 1200253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b0ea739bb4eccab4d58905eeaaf67795303552dba62f11014454f83907e5731" } } ], "extra": [ 1, 167, 253, 51, 232, 181, 108, 142, 64, 124, 28, 42, 242, 254, 167, 207, 118, 34, 103, 230, 104, 181, 91, 2, 91, 142, 218, 181, 160, 59, 145, 203, 134, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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