Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e25a57289491c29ad0eb0d794ee115a06a170c28247f4a16c3a30df5e4cca2ac

Tx prefix hash: d56274dd1ad4d2ffb289393a36a7a5e01dc785bf2ccbc9a1ab1840c0cd2d5ced
Tx public key: 1e2f9b8338e672d9977a55d9e5c58f32092264bb6510ce69cd9e2643d859714e
Timestamp: 1713168485 Timestamp [UCT]: 2024-04-15 08:08:05 Age [y:d:h:m:s]: 00:227:12:13:00
Block: 1000909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162879 RingCT/type: yes/0
Extra: 011e2f9b8338e672d9977a55d9e5c58f32092264bb6510ce69cd9e2643d859714e02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9b7dd0abd876e96cb7aba380025110abff6db7b83c8f7f9a3fffe4e312c427b 0.600000000000 1461409 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": 1000919, "vin": [ { "gen": { "height": 1000909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9b7dd0abd876e96cb7aba380025110abff6db7b83c8f7f9a3fffe4e312c427b" } } ], "extra": [ 1, 30, 47, 155, 131, 56, 230, 114, 217, 151, 122, 85, 217, 229, 197, 143, 50, 9, 34, 100, 187, 101, 16, 206, 105, 205, 158, 38, 67, 216, 89, 113, 78, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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