Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3134b104e6f00f71cd2d052270f870632298ae72fc1dab7a50b59562f0707ed8

Tx prefix hash: d2c845ea09ceaf275a1b1b2fa9f30e1d9533aacf46108c9041fd95e83d14db1a
Tx public key: 66a2ba708671bc2361d4623c883e314130667c98c7ae230d014bd1ca9dcd152e
Timestamp: 1695502036 Timestamp [UCT]: 2023-09-23 20:47:16 Age [y:d:h:m:s]: 01:187:12:45:59
Block: 854655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395090 RingCT/type: yes/0
Extra: 0166a2ba708671bc2361d4623c883e314130667c98c7ae230d014bd1ca9dcd152e02110000000cfaf35c9c000000000000000000

1 output(s) for total of 0.904010033000 dcy

stealth address amount amount idx
00: 5434402fec6223cf7db7e44c52e15bbf16209594b3e7ee674b52c68375e1a277 0.904010033000 1308641 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": 854665, "vin": [ { "gen": { "height": 854655 } } ], "vout": [ { "amount": 904010033, "target": { "key": "5434402fec6223cf7db7e44c52e15bbf16209594b3e7ee674b52c68375e1a277" } } ], "extra": [ 1, 102, 162, 186, 112, 134, 113, 188, 35, 97, 212, 98, 60, 136, 62, 49, 65, 48, 102, 124, 152, 199, 174, 35, 13, 1, 75, 209, 202, 157, 205, 21, 46, 2, 17, 0, 0, 0, 12, 250, 243, 92, 156, 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