Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afecf6a154558b0b08c5b556144214672e7cca79636d1a35f7018cc370dc04c4

Tx prefix hash: 65bde2a994b4033053ced092c80fe2ebd53aa4649e020a4b000cfa7f8d3d419d
Tx public key: 4706b8b58d9d5b59778848d2d7f25a9119fe7aac31a8fe9ab40b22a23d1297d8
Timestamp: 1724718767 Timestamp [UCT]: 2024-08-27 00:32:47 Age [y:d:h:m:s]: 00:293:17:01:10
Block: 1096668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209724 RingCT/type: yes/0
Extra: 014706b8b58d9d5b59778848d2d7f25a9119fe7aac31a8fe9ab40b22a23d1297d8021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58483efd220e8c40847c655c4c162e18a8bffceeefce162ed27588288ebee497 0.600000000000 1571861 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": 1096678, "vin": [ { "gen": { "height": 1096668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58483efd220e8c40847c655c4c162e18a8bffceeefce162ed27588288ebee497" } } ], "extra": [ 1, 71, 6, 184, 181, 141, 157, 91, 89, 119, 136, 72, 210, 215, 242, 90, 145, 25, 254, 122, 172, 49, 168, 254, 154, 180, 11, 34, 162, 61, 18, 151, 216, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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