Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 639fcd1442c13354f63a842fb55d27ffeed64a3ba47b5227f51dc74f5c0d490a

Tx prefix hash: f6989a7c6fc449128352029d39d2a1909a7990fe8df8d824710e1b167bb47a7f
Tx public key: b85ea5e395ed7ce0685b973de6dc2ee289ecf4a7f67a84b61de4286c9be0610e
Timestamp: 1719892202 Timestamp [UCT]: 2024-07-02 03:50:02 Age [y:d:h:m:s]: 01:132:04:20:49
Block: 1056654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353011 RingCT/type: yes/0
Extra: 01b85ea5e395ed7ce0685b973de6dc2ee289ecf4a7f67a84b61de4286c9be0610e02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f917c58cd16bb71d3bbd7919a59b1054f807039d742e3a10a269e4eb0c0e174 0.600000000000 1527071 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": 1056664, "vin": [ { "gen": { "height": 1056654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f917c58cd16bb71d3bbd7919a59b1054f807039d742e3a10a269e4eb0c0e174" } } ], "extra": [ 1, 184, 94, 165, 227, 149, 237, 124, 224, 104, 91, 151, 61, 230, 220, 46, 226, 137, 236, 244, 167, 246, 122, 132, 182, 29, 228, 40, 108, 155, 224, 97, 14, 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