Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 656d0c3610620584a93a0cd5710be81ec26426b97e0a0b95d9316adc99992347

Tx prefix hash: f3c0da5677179f312032f37a0e7e55649aecb09bc7b711d26b1cab0e7570ccaf
Tx public key: b7dd4dacdaff3e9c6e9a35d4902effd470794a039448ac06d81ddfa830b691d5
Timestamp: 1702945033 Timestamp [UCT]: 2023-12-19 00:17:13 Age [y:d:h:m:s]: 01:130:09:36:12
Block: 916162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354344 RingCT/type: yes/0
Extra: 01b7dd4dacdaff3e9c6e9a35d4902effd470794a039448ac06d81ddfa830b691d5021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26846bb10b3fcdba4cec9ac1daa77b62acec27d7f55a4fbc2f51a2d11630c228 0.600000000000 1373644 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": 916172, "vin": [ { "gen": { "height": 916162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26846bb10b3fcdba4cec9ac1daa77b62acec27d7f55a4fbc2f51a2d11630c228" } } ], "extra": [ 1, 183, 221, 77, 172, 218, 255, 62, 156, 110, 154, 53, 212, 144, 46, 255, 212, 112, 121, 74, 3, 148, 72, 172, 6, 216, 29, 223, 168, 48, 182, 145, 213, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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