Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36a1284cb2ced04637c087922c28fe938eaf9b556e2ebf2b1a2e34bed9051789

Tx prefix hash: b1c97d95509152947f6dd74d37159c6552726c5e44390ea22b40be71fa22405d
Tx public key: 849c7aa53b612cb740c8d66fad4c44f365904deeadd279363276951ccb4c3425
Timestamp: 1708618367 Timestamp [UCT]: 2024-02-22 16:12:47 Age [y:d:h:m:s]: 01:040:22:06:01
Block: 963194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290265 RingCT/type: yes/0
Extra: 01849c7aa53b612cb740c8d66fad4c44f365904deeadd279363276951ccb4c34250211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5f67d1d5383d04599b573e67e077afc6992f4b635c231d5c9fad3dbd68ff3e8 0.600000000000 1422893 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": 963204, "vin": [ { "gen": { "height": 963194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5f67d1d5383d04599b573e67e077afc6992f4b635c231d5c9fad3dbd68ff3e8" } } ], "extra": [ 1, 132, 156, 122, 165, 59, 97, 44, 183, 64, 200, 214, 111, 173, 76, 68, 243, 101, 144, 77, 238, 173, 210, 121, 54, 50, 118, 149, 28, 203, 76, 52, 37, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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