Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99f9f76aa9d23707ce3f71d19a24c7235ecfade006e9c7e7bb76c2cb4ee574ce

Tx prefix hash: bd3c7067a0fa7854b48d0c6de0004ddbd8fd2874c70c90b00f771188624f71c1
Tx public key: b2b4f63657e81615adc406fd06bf02b458a16d0faa722daaf8234bae49c0f271
Timestamp: 1723988430 Timestamp [UCT]: 2024-08-18 13:40:30 Age [y:d:h:m:s]: 01:080:13:27:05
Block: 1090630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316016 RingCT/type: yes/0
Extra: 01b2b4f63657e81615adc406fd06bf02b458a16d0faa722daaf8234bae49c0f27102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4f1e5201456a8d91bd7dabb8a5cab43ceab88e50b9d5d100a513cf787a19a18 0.600000000000 1565253 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": 1090640, "vin": [ { "gen": { "height": 1090630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4f1e5201456a8d91bd7dabb8a5cab43ceab88e50b9d5d100a513cf787a19a18" } } ], "extra": [ 1, 178, 180, 246, 54, 87, 232, 22, 21, 173, 196, 6, 253, 6, 191, 2, 180, 88, 161, 109, 15, 170, 114, 45, 170, 248, 35, 75, 174, 73, 192, 242, 113, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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