Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d276e3e153f0e578d086a3687d0804857db4ec3a75fdd3259136c70fd0aa126

Tx prefix hash: 2ce898d62924c93a7b16dc695ce0dd31bfe14368ba62e12725de1bc25ccb356d
Tx public key: 6dee26fc311d4007e053b98834b6fd5d0ae680d29619dc9fec2b6c3162b63ae7
Timestamp: 1726496211 Timestamp [UCT]: 2024-09-16 14:16:51 Age [y:d:h:m:s]: 00:199:06:09:21
Block: 1111410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142229 RingCT/type: yes/0
Extra: 016dee26fc311d4007e053b98834b6fd5d0ae680d29619dc9fec2b6c3162b63ae702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7d2e5adbf4f488a8128c0783f57ead8adbb42a95f99eb5ed301f177ebab664d 0.600000000000 1590359 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": 1111420, "vin": [ { "gen": { "height": 1111410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7d2e5adbf4f488a8128c0783f57ead8adbb42a95f99eb5ed301f177ebab664d" } } ], "extra": [ 1, 109, 238, 38, 252, 49, 29, 64, 7, 224, 83, 185, 136, 52, 182, 253, 93, 10, 230, 128, 210, 150, 25, 220, 159, 236, 43, 108, 49, 98, 182, 58, 231, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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