Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9789e27621ed2c11801c3204eb0ca81786c30248692debc89d8e592f34ca2f1

Tx prefix hash: 0257d9a364bd398aa8a47b0725745e68a528d3af821dcce84a59dd3dbe2ae21a
Tx public key: bf66f47b70b892595e15fae9ceb3675c5c181888b2ebcabfcab729319698e18e
Timestamp: 1700615891 Timestamp [UCT]: 2023-11-22 01:18:11 Age [y:d:h:m:s]: 01:140:21:31:42
Block: 896851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361868 RingCT/type: yes/0
Extra: 01bf66f47b70b892595e15fae9ceb3675c5c181888b2ebcabfcab729319698e18e02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.655179536000 dcy

stealth address amount amount idx
00: d05db3418d346c0171df96378133f634edc00dc2d4709e64f3594fe6a9d0bae4 0.655179536000 1353194 of 0

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": 896861, "vin": [ { "gen": { "height": 896851 } } ], "vout": [ { "amount": 655179536, "target": { "key": "d05db3418d346c0171df96378133f634edc00dc2d4709e64f3594fe6a9d0bae4" } } ], "extra": [ 1, 191, 102, 244, 123, 112, 184, 146, 89, 94, 21, 250, 233, 206, 179, 103, 92, 92, 24, 24, 136, 178, 235, 202, 191, 202, 183, 41, 49, 150, 152, 225, 142, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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