Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78064c499ccc6c80481112e9c0b0f5d49696931942db290e6a585eca5e7659b8

Tx prefix hash: 1aa90c3820b1eebe2e4219b8e9ee26ce275bcdd279b6ed4fb8eed065ffecc6cc
Tx public key: 01bd5ceb4eab146d2027e88a53567f7598b2af6cffca79340f15d57f591811c0
Timestamp: 1723666715 Timestamp [UCT]: 2024-08-14 20:18:35 Age [y:d:h:m:s]: 00:257:20:05:44
Block: 1087950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184179 RingCT/type: yes/0
Extra: 0101bd5ceb4eab146d2027e88a53567f7598b2af6cffca79340f15d57f591811c002110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a613e636d4d80fb983f33e12c2684b0d2438efa223855c686513a3a1c9f7b3f 0.600000000000 1562561 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": 1087960, "vin": [ { "gen": { "height": 1087950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a613e636d4d80fb983f33e12c2684b0d2438efa223855c686513a3a1c9f7b3f" } } ], "extra": [ 1, 1, 189, 92, 235, 78, 171, 20, 109, 32, 39, 232, 138, 83, 86, 127, 117, 152, 178, 175, 108, 255, 202, 121, 52, 15, 21, 213, 127, 89, 24, 17, 192, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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