Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfdd9f5c0b4fdef0c33379a244759e0e42607c6fdd6453785439295403356a25

Tx prefix hash: 6ff6db3d050feca0cf72e2c47dda83a2b4695ca8b7c2d7cb73e5ca564f4b317e
Tx public key: 0ebd23c9b6b0b0a844269f0b33dc6c3777b6e7fedb7470f216b16b6ee173d888
Timestamp: 1661904180 Timestamp [UCT]: 2022-08-31 00:03:00 Age [y:d:h:m:s]: 02:274:21:12:51
Block: 577394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 717776 RingCT/type: yes/0
Extra: 010ebd23c9b6b0b0a844269f0b33dc6c3777b6e7fedb7470f216b16b6ee173d88802110000000675e3f0e9000000000000000000

1 output(s) for total of 7.496422966000 dcy

stealth address amount amount idx
00: 0f5eb982f08acfdde31f7686403953e9404eaae2466f20940adbdd79b843e263 7.496422966000 1010786 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": 577404, "vin": [ { "gen": { "height": 577394 } } ], "vout": [ { "amount": 7496422966, "target": { "key": "0f5eb982f08acfdde31f7686403953e9404eaae2466f20940adbdd79b843e263" } } ], "extra": [ 1, 14, 189, 35, 201, 182, 176, 176, 168, 68, 38, 159, 11, 51, 220, 108, 55, 119, 182, 231, 254, 219, 116, 112, 242, 22, 177, 107, 110, 225, 115, 216, 136, 2, 17, 0, 0, 0, 6, 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