Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ec5105e71ea466d375bed50af95f1ffbbd4f9b92aac179fede6490c647b1bda

Tx prefix hash: 24b03d78ddd335cfd919263807be4d3891feba8b44ddaff6d4d4c6febd8de1c9
Tx public key: 9d319164b1e9792e28cd3c2884c0ffde8e4d0c4c97914d6abd25db14c0915689
Timestamp: 1718516523 Timestamp [UCT]: 2024-06-16 05:42:03 Age [y:d:h:m:s]: 00:222:05:41:49
Block: 1045274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158972 RingCT/type: yes/0
Extra: 019d319164b1e9792e28cd3c2884c0ffde8e4d0c4c97914d6abd25db14c0915689021100000001f0f115fa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3f0273fe53d5110aba38a489efe5e3514acf097b805d0ffc1ae8e95dacdb362 0.600000000000 1514799 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": 1045284, "vin": [ { "gen": { "height": 1045274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3f0273fe53d5110aba38a489efe5e3514acf097b805d0ffc1ae8e95dacdb362" } } ], "extra": [ 1, 157, 49, 145, 100, 177, 233, 121, 46, 40, 205, 60, 40, 132, 192, 255, 222, 142, 77, 12, 76, 151, 145, 77, 106, 189, 37, 219, 20, 192, 145, 86, 137, 2, 17, 0, 0, 0, 1, 240, 241, 21, 250, 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