Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 172dda975305a06c180b4aeb0b1e4edef28a7bf7169a4e3ea5c5f48f31c280d2

Tx prefix hash: 75e63c102489e4a7832c721df906f4e6a68dbf628bbcf9d15f93834731f1962d
Tx public key: 6abd80e21b46caeea110d54d9942291002894f6f11358fbf0e6a05d2ab287f0a
Timestamp: 1716244088 Timestamp [UCT]: 2024-05-20 22:28:08 Age [y:d:h:m:s]: 00:191:21:01:43
Block: 1026418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137342 RingCT/type: yes/0
Extra: 016abd80e21b46caeea110d54d9942291002894f6f11358fbf0e6a05d2ab287f0a02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fe9ceeb0ee03fa7960364486070cb29ff01330038c2c19c52c7767b4c3caa75 0.600000000000 1493497 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": 1026428, "vin": [ { "gen": { "height": 1026418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fe9ceeb0ee03fa7960364486070cb29ff01330038c2c19c52c7767b4c3caa75" } } ], "extra": [ 1, 106, 189, 128, 226, 27, 70, 202, 238, 161, 16, 213, 77, 153, 66, 41, 16, 2, 137, 79, 111, 17, 53, 143, 191, 14, 106, 5, 210, 171, 40, 127, 10, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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