Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f928cd4d4fd12d5ca2baa6457251574eeff93e4bcd5b917a687555f1b2251cd8

Tx prefix hash: 8362d39963e5b58cbf1062ec44b18e9298df6f11f01a8a6e7403d59a0f6819a5
Tx public key: e5ec3a2130503ec13c72dd015a7da645361b14f71d8b84b7ad21ab239179e8e0
Timestamp: 1711109381 Timestamp [UCT]: 2024-03-22 12:09:41 Age [y:d:h:m:s]: 01:039:09:37:30
Block: 983871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289120 RingCT/type: yes/0
Extra: 01e5ec3a2130503ec13c72dd015a7da645361b14f71d8b84b7ad21ab239179e8e002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac1ab2dc6850b95203dd3e5f60c05922793fcc8f0c86f91799487b8013792807 0.600000000000 1444024 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": 983881, "vin": [ { "gen": { "height": 983871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac1ab2dc6850b95203dd3e5f60c05922793fcc8f0c86f91799487b8013792807" } } ], "extra": [ 1, 229, 236, 58, 33, 48, 80, 62, 193, 60, 114, 221, 1, 90, 125, 166, 69, 54, 27, 20, 247, 29, 139, 132, 183, 173, 33, 171, 35, 145, 121, 232, 224, 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