Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc6de6c68c33594e33dd7f7b4e2108c359937be559f5fb9e1e16836c58b8bc6a

Tx prefix hash: d973328d077d00d5ed74429df3379b254b95eec01924aac0d12e1155d8df1981
Tx public key: 0e2490a32c814cef7b56ae4c8ec24fef0d82444d1c13261d8e58d4264a065368
Timestamp: 1714180056 Timestamp [UCT]: 2024-04-27 01:07:36 Age [y:d:h:m:s]: 00:343:21:52:18
Block: 1009296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245853 RingCT/type: yes/0
Extra: 010e2490a32c814cef7b56ae4c8ec24fef0d82444d1c13261d8e58d4264a06536802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4d6198fda8720cbe9e8a03a3ed1cb5b66d536ea198c1a68dee1c56334afcace 0.600000000000 1470928 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": 1009306, "vin": [ { "gen": { "height": 1009296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4d6198fda8720cbe9e8a03a3ed1cb5b66d536ea198c1a68dee1c56334afcace" } } ], "extra": [ 1, 14, 36, 144, 163, 44, 129, 76, 239, 123, 86, 174, 76, 142, 194, 79, 239, 13, 130, 68, 77, 28, 19, 38, 29, 142, 88, 212, 38, 74, 6, 83, 104, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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