Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10d80af1dc8ebafc80af57415a2f8918980c306b008033a9bebd3a7996771fbd

Tx prefix hash: 837ca2060c72e12bf843c5640a272ff8a793bcb85a2a226cc736137e3f1e06bd
Tx public key: a8491c72c51692d34e9d7332499ebcadd16f8020e2912b6c06605321722f86ee
Timestamp: 1709224593 Timestamp [UCT]: 2024-02-29 16:36:33 Age [y:d:h:m:s]: 01:099:02:42:46
Block: 968231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331884 RingCT/type: yes/0
Extra: 01a8491c72c51692d34e9d7332499ebcadd16f8020e2912b6c06605321722f86ee02110000000c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fcc811fdc0e5cc09d3f34bc96220f7f8126a6c09afbe6813fef9e92e28c7a4e 0.600000000000 1428032 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": 968241, "vin": [ { "gen": { "height": 968231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fcc811fdc0e5cc09d3f34bc96220f7f8126a6c09afbe6813fef9e92e28c7a4e" } } ], "extra": [ 1, 168, 73, 28, 114, 197, 22, 146, 211, 78, 157, 115, 50, 73, 158, 188, 173, 209, 111, 128, 32, 226, 145, 43, 108, 6, 96, 83, 33, 114, 47, 134, 238, 2, 17, 0, 0, 0, 12, 82, 212, 126, 148, 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