Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38a36432427d4411fdbc40c973e6f852a00b8288b2dbd52404fb638fce461aeb

Tx prefix hash: ca271e7d276bec615f210b750ab5d0e2b4d08c7d9e712284891a50e6473ef175
Tx public key: 0c6ff67a33c94bca2cbdbda2e30bf970f1e2f3d8edd550a8fdfd5fb3f912e98c
Timestamp: 1717972902 Timestamp [UCT]: 2024-06-09 22:41:42 Age [y:d:h:m:s]: 00:279:17:13:00
Block: 1040745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199908 RingCT/type: yes/0
Extra: 010c6ff67a33c94bca2cbdbda2e30bf970f1e2f3d8edd550a8fdfd5fb3f912e98c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd6e086346eb199baf264101be086f7b9554d4fcc0bead3ce6cd26e75ac84aca 0.600000000000 1509406 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": 1040755, "vin": [ { "gen": { "height": 1040745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd6e086346eb199baf264101be086f7b9554d4fcc0bead3ce6cd26e75ac84aca" } } ], "extra": [ 1, 12, 111, 246, 122, 51, 201, 75, 202, 44, 189, 189, 162, 227, 11, 249, 112, 241, 226, 243, 216, 237, 213, 80, 168, 253, 253, 95, 179, 249, 18, 233, 140, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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