Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ce68c5519d6a795c370a943958763664af62cbb16e28e544a62b16b2b0e47ac

Tx prefix hash: c59148324b5f86049c6d178e9c8711b77790f096a3e5e6048e974ae771c03165
Tx public key: b1d0a04a158717da9b3b412cf099a1277d46c14d3597f5e3f53dcba9867547f8
Timestamp: 1744487787 Timestamp [UCT]: 2025-04-12 19:56:27 Age [y:d:h:m:s]: 00:025:06:01:10
Block: 1260066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18063 RingCT/type: yes/0
Extra: 01b1d0a04a158717da9b3b412cf099a1277d46c14d3597f5e3f53dcba9867547f8021100000009dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd2565f7db47ac34bc1295c74f272b585624b83d9866c7da287796252109b77a 0.600000000000 1747217 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": 1260076, "vin": [ { "gen": { "height": 1260066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd2565f7db47ac34bc1295c74f272b585624b83d9866c7da287796252109b77a" } } ], "extra": [ 1, 177, 208, 160, 74, 21, 135, 23, 218, 155, 59, 65, 44, 240, 153, 161, 39, 125, 70, 193, 77, 53, 151, 245, 227, 245, 61, 203, 169, 134, 117, 71, 248, 2, 17, 0, 0, 0, 9, 219, 181, 113, 193, 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