Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c70cf75d666eea9cc3483d21099248d9d3980152fb5a8962def5fa5f24a53f3

Tx prefix hash: e94c860d08d1902a37dd9212a72f7b27f3c44365c4bd8a32a40010ee02288ceb
Tx public key: b2fb5a31e843b4ce4f69fe19bdf6c3998955a452ed51b4c6623d7637194c5fdb
Timestamp: 1705121108 Timestamp [UCT]: 2024-01-13 04:45:08 Age [y:d:h:m:s]: 00:363:22:29:00
Block: 934182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260560 RingCT/type: yes/0
Extra: 01b2fb5a31e843b4ce4f69fe19bdf6c3998955a452ed51b4c6623d7637194c5fdb0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c8e9a2beeafa06f03096149a08cc5f280d659379bc5d640f065b76d109d1a4e 0.600000000000 1392170 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": 934192, "vin": [ { "gen": { "height": 934182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c8e9a2beeafa06f03096149a08cc5f280d659379bc5d640f065b76d109d1a4e" } } ], "extra": [ 1, 178, 251, 90, 49, 232, 67, 180, 206, 79, 105, 254, 25, 189, 246, 195, 153, 137, 85, 164, 82, 237, 81, 180, 198, 98, 61, 118, 55, 25, 76, 95, 219, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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