Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85d74f840577f8e7cfcdf7c70b71f33c8c1e40b6189fe00e54a10525ab530b99

Tx prefix hash: 72325d9237a4effb270fe1367b6298fb5a0a377efbea2196c7802895774844bb
Tx public key: acde31e0a6b8f4c3e50876d5fce0e86fcd0d9be71fc96be8f3db9506add328a0
Timestamp: 1718658122 Timestamp [UCT]: 2024-06-17 21:02:02 Age [y:d:h:m:s]: 00:218:09:47:20
Block: 1046432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156247 RingCT/type: yes/0
Extra: 01acde31e0a6b8f4c3e50876d5fce0e86fcd0d9be71fc96be8f3db9506add328a002110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c29a168f393da9de11397a77a56988de57a20d6781b478eea1ede83e506a04a 0.600000000000 1516245 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": 1046442, "vin": [ { "gen": { "height": 1046432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c29a168f393da9de11397a77a56988de57a20d6781b478eea1ede83e506a04a" } } ], "extra": [ 1, 172, 222, 49, 224, 166, 184, 244, 195, 229, 8, 118, 213, 252, 224, 232, 111, 205, 13, 155, 231, 31, 201, 107, 232, 243, 219, 149, 6, 173, 211, 40, 160, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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