Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb95acb70af9abc1ffe395c74cb9e902c6c479815ca415246d990c2db60170cc

Tx prefix hash: 476cbf0816c055cd6394340603032833fdd30c865329328c522fe9b3e2d9a3a4
Tx public key: 4409b4c3850d3f7451dc099951c230d464748d1abb302fa5fc5e7e214feddbd6
Timestamp: 1731508528 Timestamp [UCT]: 2024-11-13 14:35:28 Age [y:d:h:m:s]: 00:140:22:33:33
Block: 1152878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100547 RingCT/type: yes/0
Extra: 014409b4c3850d3f7451dc099951c230d464748d1abb302fa5fc5e7e214feddbd60211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 543b6632615d62b00df78a0c2b4184b4d0b6b60a0971d00f92092e209568acea 0.600000000000 1638483 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": 1152888, "vin": [ { "gen": { "height": 1152878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "543b6632615d62b00df78a0c2b4184b4d0b6b60a0971d00f92092e209568acea" } } ], "extra": [ 1, 68, 9, 180, 195, 133, 13, 63, 116, 81, 220, 9, 153, 81, 194, 48, 212, 100, 116, 141, 26, 187, 48, 47, 165, 252, 94, 126, 33, 79, 237, 219, 214, 2, 17, 0, 0, 0, 2, 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