Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d049587bb08e08c5f613ffc54008bc5fae0d2518e4c4de73216d3979c89cb72

Tx prefix hash: 8874e199b4bd95a16b5a518558c94a3fd8a4f2417a6106a8b8590418b325cb43
Tx public key: f80cf7b52f0a4209fe9f0f3608f3fb13943b3e6a0f278a61d5c3f195fc90b11d
Timestamp: 1696613232 Timestamp [UCT]: 2023-10-06 17:27:12 Age [y:d:h:m:s]: 01:115:04:42:32
Block: 863867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343356 RingCT/type: yes/0
Extra: 01f80cf7b52f0a4209fe9f0f3608f3fb13943b3e6a0f278a61d5c3f195fc90b11d0211000000044b8f5122000000000000000000

1 output(s) for total of 0.842655495000 dcy

stealth address amount amount idx
00: 874a84e318468b237b868fa26c792800724b0fdd3ad9524a8f261b202a4bff06 0.842655495000 1318363 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": 863877, "vin": [ { "gen": { "height": 863867 } } ], "vout": [ { "amount": 842655495, "target": { "key": "874a84e318468b237b868fa26c792800724b0fdd3ad9524a8f261b202a4bff06" } } ], "extra": [ 1, 248, 12, 247, 181, 47, 10, 66, 9, 254, 159, 15, 54, 8, 243, 251, 19, 148, 59, 62, 106, 15, 39, 138, 97, 213, 195, 241, 149, 252, 144, 177, 29, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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