Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b854e23f58b1cba01ecdb17e83d4a2122c9a85afdb6f39d64a45a9cb1ff2899e

Tx prefix hash: 9ac34349ac745821aac865e255f4b52321daed4e6def01c66caf90b58515e1e4
Tx public key: 7ba751dd9a9658d7ed495551408d9d96151b2c29393c9198696c98ebf0f236bd
Timestamp: 1703289975 Timestamp [UCT]: 2023-12-23 00:06:15 Age [y:d:h:m:s]: 01:326:16:36:10
Block: 919021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492332 RingCT/type: yes/0
Extra: 017ba751dd9a9658d7ed495551408d9d96151b2c29393c9198696c98ebf0f236bd0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c000d7a3bef0c40e0aa67fd0b46d743afb15addc423baddcf0cc1cba99effa7 0.600000000000 1376685 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": 919031, "vin": [ { "gen": { "height": 919021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c000d7a3bef0c40e0aa67fd0b46d743afb15addc423baddcf0cc1cba99effa7" } } ], "extra": [ 1, 123, 167, 81, 221, 154, 150, 88, 215, 237, 73, 85, 81, 64, 141, 157, 150, 21, 27, 44, 41, 57, 60, 145, 152, 105, 108, 152, 235, 240, 242, 54, 189, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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