Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d40b3460e9d13cdede50332d8142385a1b4b68839f981dff0287fd7374cf57b8

Tx prefix hash: 08a907ad3f64117bb2f1a486819e1bb6f31fa415d9b7d0004d0e3a25994eb502
Tx public key: 0ff1264d3c82b2bcb8ad91392d376bb062b212d2eb44acc1165713b838474589
Timestamp: 1696795323 Timestamp [UCT]: 2023-10-08 20:02:03 Age [y:d:h:m:s]: 01:096:00:47:55
Block: 865388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329877 RingCT/type: yes/0
Extra: 010ff1264d3c82b2bcb8ad91392d376bb062b212d2eb44acc1165713b83847458902110000000141ee1c9b000000000000000000

1 output(s) for total of 0.832933540000 dcy

stealth address amount amount idx
00: 6332a3a4380c68700f39f7f30280dc05959ee0411a7b9efa875fcf4390ff83ff 0.832933540000 1319920 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": 865398, "vin": [ { "gen": { "height": 865388 } } ], "vout": [ { "amount": 832933540, "target": { "key": "6332a3a4380c68700f39f7f30280dc05959ee0411a7b9efa875fcf4390ff83ff" } } ], "extra": [ 1, 15, 241, 38, 77, 60, 130, 178, 188, 184, 173, 145, 57, 45, 55, 107, 176, 98, 178, 18, 210, 235, 68, 172, 193, 22, 87, 19, 184, 56, 71, 69, 137, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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