Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50929e29ec3ffa5c09a04d26a381768dfe8edb863b6fe8c670b8f3e777143401

Tx prefix hash: 754a0d4467fc5309dafd9926ce1b0fd5db4e77bbc662c2663a16379668978c35
Tx public key: d44f15b0ab6103382cd6e4d16d48ef12e49bcec53ff0e487f20f61d278fca1c5
Timestamp: 1711143277 Timestamp [UCT]: 2024-03-22 21:34:37 Age [y:d:h:m:s]: 01:230:09:43:10
Block: 984151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423336 RingCT/type: yes/0
Extra: 01d44f15b0ab6103382cd6e4d16d48ef12e49bcec53ff0e487f20f61d278fca1c50211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7eb92dbd74c483c5e42dee50e52d0df4ab99db5b653587528c2af9d22f28a314 0.600000000000 1444312 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": 984161, "vin": [ { "gen": { "height": 984151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7eb92dbd74c483c5e42dee50e52d0df4ab99db5b653587528c2af9d22f28a314" } } ], "extra": [ 1, 212, 79, 21, 176, 171, 97, 3, 56, 44, 214, 228, 209, 109, 72, 239, 18, 228, 155, 206, 197, 63, 240, 228, 135, 242, 15, 97, 210, 120, 252, 161, 197, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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