Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8692a75c35ca774c3c8732db1da4532e150db0a113c9d58e0c78d41bdc22ce4

Tx prefix hash: 498a3e8824a0562298ece2583ff0bba82ce503d659d71c0f15e0998deb8564db
Tx public key: 23eef9a8a157a8596eea1d30bf7ae2c18520165e0f676080b3eeef15e31ff1de
Timestamp: 1647687831 Timestamp [UCT]: 2022-03-19 11:03:51 Age [y:d:h:m:s]: 02:279:19:07:18
Block: 461764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 719514 RingCT/type: yes/0
Extra: 0123eef9a8a157a8596eea1d30bf7ae2c18520165e0f676080b3eeef15e31ff1de021100000004cb8520c2000000000000000000

1 output(s) for total of 18.112752058000 dcy

stealth address amount amount idx
00: e80b1db5b16f9b3755be14471c596a80578dcd0da340b8a7b6e9fd5ff3dbad80 18.112752058000 879077 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": 461774, "vin": [ { "gen": { "height": 461764 } } ], "vout": [ { "amount": 18112752058, "target": { "key": "e80b1db5b16f9b3755be14471c596a80578dcd0da340b8a7b6e9fd5ff3dbad80" } } ], "extra": [ 1, 35, 238, 249, 168, 161, 87, 168, 89, 110, 234, 29, 48, 191, 122, 226, 193, 133, 32, 22, 94, 15, 103, 96, 128, 179, 238, 239, 21, 227, 31, 241, 222, 2, 17, 0, 0, 0, 4, 203, 133, 32, 194, 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