Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d30c818a06ccf74aa2bbcc4b5460f87985900dcd60722e36af11e0fa7958a49

Tx prefix hash: 3fa93922b00bd08195c9748608fc375c85e68dbad2fff7f1b3e279088d11f9d4
Tx public key: 6e1e07f523ab40159775438bf805026ed2f893f93d0bceec3f6fae44175a3a0c
Timestamp: 1720567578 Timestamp [UCT]: 2024-07-09 23:26:18 Age [y:d:h:m:s]: 00:172:18:38:28
Block: 1062271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123615 RingCT/type: yes/0
Extra: 016e1e07f523ab40159775438bf805026ed2f893f93d0bceec3f6fae44175a3a0c02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91e42d245643feea1a7638db219e55df8c5dc52f0de9aff47a9cbb75043d7fb1 0.600000000000 1532772 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": 1062281, "vin": [ { "gen": { "height": 1062271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91e42d245643feea1a7638db219e55df8c5dc52f0de9aff47a9cbb75043d7fb1" } } ], "extra": [ 1, 110, 30, 7, 245, 35, 171, 64, 21, 151, 117, 67, 139, 248, 5, 2, 110, 210, 248, 147, 249, 61, 11, 206, 236, 63, 111, 174, 68, 23, 90, 58, 12, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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