Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0a3ca076683970ca840101cd708910fc41f14c13bb77bc565a0a0fbb8145084

Tx prefix hash: d4734148962aef6b2eeb2c6317fba3240f29158393480e08f8e6f6584693bd06
Tx public key: dfa1c3e6c7091b371261731b92adf92cb5d9d1cd167da6d17517c7f7f723dc16
Timestamp: 1708471447 Timestamp [UCT]: 2024-02-20 23:24:07 Age [y:d:h:m:s]: 01:266:14:19:10
Block: 961974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449289 RingCT/type: yes/0
Extra: 01dfa1c3e6c7091b371261731b92adf92cb5d9d1cd167da6d17517c7f7f723dc160211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1889b8ae3ec6df1c5044081f423417a2efdea959e4852cb9db4c0c757a65b895 0.600000000000 1421597 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": 961984, "vin": [ { "gen": { "height": 961974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1889b8ae3ec6df1c5044081f423417a2efdea959e4852cb9db4c0c757a65b895" } } ], "extra": [ 1, 223, 161, 195, 230, 199, 9, 27, 55, 18, 97, 115, 27, 146, 173, 249, 44, 181, 217, 209, 205, 22, 125, 166, 209, 117, 23, 199, 247, 247, 35, 220, 22, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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