Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e3cb29910d588fa5a00ee0a28fbb6dd3298b8a1e9a551699e1f932f7a42e9f7

Tx prefix hash: a37f47a9e09eb783eb67eda9c7bcdaaff13d7b947948c7f68efc1bcdd4f24788
Tx public key: 9e1dd022b122448b8e9cacaaa27578a09406b4ead6fd42197a8db58ba362b145
Timestamp: 1696527586 Timestamp [UCT]: 2023-10-05 17:39:46 Age [y:d:h:m:s]: 01:098:21:22:37
Block: 863160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331939 RingCT/type: yes/0
Extra: 019e1dd022b122448b8e9cacaaa27578a09406b4ead6fd42197a8db58ba362b14502110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.847213061000 dcy

stealth address amount amount idx
00: 781bbb29e5bf768afc7c1b9c3898e6f76f28c81f26f6318c75f96ff4093c0a95 0.847213061000 1317608 of 0

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": 863170, "vin": [ { "gen": { "height": 863160 } } ], "vout": [ { "amount": 847213061, "target": { "key": "781bbb29e5bf768afc7c1b9c3898e6f76f28c81f26f6318c75f96ff4093c0a95" } } ], "extra": [ 1, 158, 29, 208, 34, 177, 34, 68, 139, 142, 156, 172, 170, 162, 117, 120, 160, 148, 6, 180, 234, 214, 253, 66, 25, 122, 141, 181, 139, 163, 98, 177, 69, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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