Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79b85961875a4d9476d0a1c2876d4c08ca83a416eeb6199ff436b8e2750dd9ba

Tx prefix hash: 50c92c7cfcb5ecf36e8e37292e1d1a49e1e875081973a1e0f08c20a55812c1ff
Tx public key: 8f8c28b7fe0b36eaf9406cb4b96097868c4cae4a2da48549d27e628849825073
Timestamp: 1713453761 Timestamp [UCT]: 2024-04-18 15:22:41 Age [y:d:h:m:s]: 01:037:03:40:08
Block: 1003269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287540 RingCT/type: yes/0
Extra: 018f8c28b7fe0b36eaf9406cb4b96097868c4cae4a2da48549d27e62884982507302110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38ff9f91891607835c4c7923894c3de5406c6ac58e85a81c40a8bf9f166d301b 0.600000000000 1463799 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": 1003279, "vin": [ { "gen": { "height": 1003269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38ff9f91891607835c4c7923894c3de5406c6ac58e85a81c40a8bf9f166d301b" } } ], "extra": [ 1, 143, 140, 40, 183, 254, 11, 54, 234, 249, 64, 108, 180, 185, 96, 151, 134, 140, 76, 174, 74, 45, 164, 133, 73, 210, 126, 98, 136, 73, 130, 80, 115, 2, 17, 0, 0, 0, 13, 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