Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 475b84748f244bdc6427141a1b514128168dd73509e5fcef116c136eaa99f424

Tx prefix hash: 9589673e41c179fd5c58709447295aed7dd7b0558cc977e71890adcef16e6ec0
Tx public key: 6bd4ec9c28639f55c381e04befb42a5d1b1ab971da98f510e4d4096c3a713dd2
Timestamp: 1733506138 Timestamp [UCT]: 2024-12-06 17:28:58 Age [y:d:h:m:s]: 00:117:04:30:36
Block: 1169424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83543 RingCT/type: yes/0
Extra: 016bd4ec9c28639f55c381e04befb42a5d1b1ab971da98f510e4d4096c3a713dd20211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00d3944b09dd09e3d4aa89c124257b4d39eb443d9d990107c4a35debbc1d6cb9 0.600000000000 1655141 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": 1169434, "vin": [ { "gen": { "height": 1169424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00d3944b09dd09e3d4aa89c124257b4d39eb443d9d990107c4a35debbc1d6cb9" } } ], "extra": [ 1, 107, 212, 236, 156, 40, 99, 159, 85, 195, 129, 224, 75, 239, 180, 42, 93, 27, 26, 185, 113, 218, 152, 245, 16, 228, 212, 9, 108, 58, 113, 61, 210, 2, 17, 0, 0, 0, 3, 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