Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d474f051d888d20dae7eee712d2abd49fce029d34a5a357a7b348955c039115

Tx prefix hash: 67e2bdb1c220802c528c4e9c42c196bda13d1514db94b669666fd0f175e8ec34
Tx public key: a73869b00f9f7bb0aa4e2850c58b511960564ec7f4507429c15d4ac4d1f9075c
Timestamp: 1717781489 Timestamp [UCT]: 2024-06-07 17:31:29 Age [y:d:h:m:s]: 01:165:11:29:00
Block: 1039167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376855 RingCT/type: yes/0
Extra: 01a73869b00f9f7bb0aa4e2850c58b511960564ec7f4507429c15d4ac4d1f9075c02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1eee03dd1db65fc0969ba4138aa376b8f9034ca85d7a08eca315458bc6f071b 0.600000000000 1507786 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": 1039177, "vin": [ { "gen": { "height": 1039167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1eee03dd1db65fc0969ba4138aa376b8f9034ca85d7a08eca315458bc6f071b" } } ], "extra": [ 1, 167, 56, 105, 176, 15, 159, 123, 176, 170, 78, 40, 80, 197, 139, 81, 25, 96, 86, 78, 199, 244, 80, 116, 41, 193, 93, 74, 196, 209, 249, 7, 92, 2, 17, 0, 0, 0, 5, 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