Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a9583ee059b1d1e3e2a35c843c908be625f1a4010b79b5047de244c73d0ba25

Tx prefix hash: 677587f625c7f5413bc3ea6a0cf57bfa7b4d05ac93dbd442340822c5a727777e
Tx public key: 7e6322fa879ab427aabaa54aaf35bf6ec71f499e0fb863b10aa872130afb7e18
Timestamp: 1706654524 Timestamp [UCT]: 2024-01-30 22:42:04 Age [y:d:h:m:s]: 00:351:18:12:14
Block: 946893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251840 RingCT/type: yes/0
Extra: 017e6322fa879ab427aabaa54aaf35bf6ec71f499e0fb863b10aa872130afb7e1802110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed27ba804efde2619384093c79594715ac44f9b57b91fd9afb64ee7670f73b9f 0.600000000000 1405237 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": 946903, "vin": [ { "gen": { "height": 946893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed27ba804efde2619384093c79594715ac44f9b57b91fd9afb64ee7670f73b9f" } } ], "extra": [ 1, 126, 99, 34, 250, 135, 154, 180, 39, 170, 186, 165, 74, 175, 53, 191, 110, 199, 31, 73, 158, 15, 184, 99, 177, 10, 168, 114, 19, 10, 251, 126, 24, 2, 17, 0, 0, 0, 5, 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