Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cec82f8663dfe377f8540be634e575ec7e90cc34f935032209a10c0f150e0c47

Tx prefix hash: 9369de1fd58a9b338f04e89918fc6b0c3e598faac59f83af78b004b25fb24375
Tx public key: 3f86243d71c686887e04cb66378702253839b3c4a5ef9f8f858d3c7e3c0416b8
Timestamp: 1699274813 Timestamp [UCT]: 2023-11-06 12:46:53 Age [y:d:h:m:s]: 01:162:17:05:34
Block: 885734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377496 RingCT/type: yes/0
Extra: 013f86243d71c686887e04cb66378702253839b3c4a5ef9f8f858d3c7e3c0416b802110000000afaf35c9c000000000000000000

1 output(s) for total of 0.713174123000 dcy

stealth address amount amount idx
00: dea6922615fedc58fdc0df8df3bf1f7ff9ab4d0da5be2e217c2eaac6c37dcf4e 0.713174123000 1341517 of 0

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": 885744, "vin": [ { "gen": { "height": 885734 } } ], "vout": [ { "amount": 713174123, "target": { "key": "dea6922615fedc58fdc0df8df3bf1f7ff9ab4d0da5be2e217c2eaac6c37dcf4e" } } ], "extra": [ 1, 63, 134, 36, 61, 113, 198, 134, 136, 126, 4, 203, 102, 55, 135, 2, 37, 56, 57, 179, 196, 165, 239, 159, 143, 133, 141, 60, 126, 60, 4, 22, 184, 2, 17, 0, 0, 0, 10, 250, 243, 92, 156, 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