Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 199ebebf935c7e4a5b3348416090fbda548a21ecae69468d185f3b54358df009

Tx prefix hash: 144ca0c71dd3280355520f7fb77b7e316f97a8db2e339b7b24b7d5df03c3c46c
Tx public key: 61d059e3d62e6120e7f98cd9b602036713d5a3a354fb0d59c115d9ebd664af03
Timestamp: 1718539392 Timestamp [UCT]: 2024-06-16 12:03:12 Age [y:d:h:m:s]: 00:191:14:26:46
Block: 1045460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137116 RingCT/type: yes/0
Extra: 0161d059e3d62e6120e7f98cd9b602036713d5a3a354fb0d59c115d9ebd664af0302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 016ac991231b787c5ce35b85866a2f436db05a39052cb960f31c034310d014e5 0.600000000000 1515039 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": 1045470, "vin": [ { "gen": { "height": 1045460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "016ac991231b787c5ce35b85866a2f436db05a39052cb960f31c034310d014e5" } } ], "extra": [ 1, 97, 208, 89, 227, 214, 46, 97, 32, 231, 249, 140, 217, 182, 2, 3, 103, 19, 213, 163, 163, 84, 251, 13, 89, 193, 21, 217, 235, 214, 100, 175, 3, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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