Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 344eb5ad7e1a724cc55228a4e3d4a76bbcf6ab1adf93c76003585bf29bdc8e03

Tx prefix hash: cda1ae2e5d8aa7ae3ec24a7f3a068851339790032e559bc8ad467d01dc2de795
Tx public key: 4cc5ae9c2cd4ad74b1f2a8edc6a46ac3936e9b8b3dded5c41b67dcea7d466743
Timestamp: 1617635057 Timestamp [UCT]: 2021-04-05 15:04:17 Age [y:d:h:m:s]: 04:036:02:17:27
Block: 233799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1046221 RingCT/type: yes/0
Extra: 014cc5ae9c2cd4ad74b1f2a8edc6a46ac3936e9b8b3dded5c41b67dcea7d4667430211000000119c1fbdcc000000000000000000

1 output(s) for total of 103.116326854000 dcy

stealth address amount amount idx
00: 1161ac9374031f801b7e40fcbf3972fa3cd91d13ce936222591c3868cbff9e0d 103.116326854000 485437 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": 233809, "vin": [ { "gen": { "height": 233799 } } ], "vout": [ { "amount": 103116326854, "target": { "key": "1161ac9374031f801b7e40fcbf3972fa3cd91d13ce936222591c3868cbff9e0d" } } ], "extra": [ 1, 76, 197, 174, 156, 44, 212, 173, 116, 177, 242, 168, 237, 198, 164, 106, 195, 147, 110, 155, 139, 61, 222, 213, 196, 27, 103, 220, 234, 125, 70, 103, 67, 2, 17, 0, 0, 0, 17, 156, 31, 189, 204, 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