Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91d09c396d2b906de7c4cfda2c45782c78dfe7b11f01612f43b164239f59f17b

Tx prefix hash: 80f0476c44a50278c8a69342b3e3ce63da5456ef1f372295b1405d451378c026
Tx public key: ca20f80b5f80d6a7276c8d892ffc3411c53ec04de0c93b56aa93a2fde2cea0de
Timestamp: 1706393763 Timestamp [UCT]: 2024-01-27 22:16:03 Age [y:d:h:m:s]: 01:331:03:40:03
Block: 944725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495534 RingCT/type: yes/0
Extra: 01ca20f80b5f80d6a7276c8d892ffc3411c53ec04de0c93b56aa93a2fde2cea0de02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a18053ee666df10cd384a7ee62fd90d691ee646004b86e25224a7e54f90d660a 0.600000000000 1403011 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": 944735, "vin": [ { "gen": { "height": 944725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a18053ee666df10cd384a7ee62fd90d691ee646004b86e25224a7e54f90d660a" } } ], "extra": [ 1, 202, 32, 248, 11, 95, 128, 214, 167, 39, 108, 141, 137, 47, 252, 52, 17, 197, 62, 192, 77, 224, 201, 59, 86, 170, 147, 162, 253, 226, 206, 160, 222, 2, 17, 0, 0, 0, 3, 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