Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d0106b37a7dd46b5a8b7c32af77bfb36918ff0c4215e5c5743d880a53c321f5

Tx prefix hash: 263dea81a99759fc5fae1882e7f103277d4f37e7b443f3d03ef26ac37344befc
Tx public key: de96620ee015b8e6ef3d4389e01f84cd90598f7c3ea2bfd9a53a380c4f4b7520
Timestamp: 1734110154 Timestamp [UCT]: 2024-12-13 17:15:54 Age [y:d:h:m:s]: 00:101:16:33:10
Block: 1174454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72437 RingCT/type: yes/0
Extra: 01de96620ee015b8e6ef3d4389e01f84cd90598f7c3ea2bfd9a53a380c4f4b75200211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17320523bec7b24ac0ed3636bc967c5b1dea51e0e9fe60e5b452cc32f923c07f 0.600000000000 1660607 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": 1174464, "vin": [ { "gen": { "height": 1174454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17320523bec7b24ac0ed3636bc967c5b1dea51e0e9fe60e5b452cc32f923c07f" } } ], "extra": [ 1, 222, 150, 98, 14, 224, 21, 184, 230, 239, 61, 67, 137, 224, 31, 132, 205, 144, 89, 143, 124, 62, 162, 191, 217, 165, 58, 56, 12, 79, 75, 117, 32, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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