Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ab4f684bec9d162ee3764eb4262e73703d86ef9bea3381ae4e465d8ed279895

Tx prefix hash: fa94083a2e16c6946ee41a6ec947d49e3246ab333b91e66b5777900e676b5fee
Tx public key: eb2e5a7fe25bf0fc77a167be9465c5cce3ad1f1bff01c57ab27d11e5c73638c4
Timestamp: 1721912640 Timestamp [UCT]: 2024-07-25 13:04:00 Age [y:d:h:m:s]: 00:317:11:31:00
Block: 1073413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226854 RingCT/type: yes/0
Extra: 01eb2e5a7fe25bf0fc77a167be9465c5cce3ad1f1bff01c57ab27d11e5c73638c402110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fa234c0b3d7a1b68cd87aa241f65b8d8736d9bfc605a5f2e7a997bc0b080143 0.600000000000 1545914 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": 1073423, "vin": [ { "gen": { "height": 1073413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fa234c0b3d7a1b68cd87aa241f65b8d8736d9bfc605a5f2e7a997bc0b080143" } } ], "extra": [ 1, 235, 46, 90, 127, 226, 91, 240, 252, 119, 161, 103, 190, 148, 101, 197, 204, 227, 173, 31, 27, 255, 1, 197, 122, 178, 125, 17, 229, 199, 54, 56, 196, 2, 17, 0, 0, 0, 7, 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