Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5da380d5709a84a5e6805bc38b908bf9f896e8a71c9b0ba5c1a8a9c4505253f6

Tx prefix hash: fd10c69573f1c33339e1a4b6d80127198e0f1c90b9fa56383ad7e5791edcd721
Tx public key: a5af58ca1059bac9c00d1a6cf3402f665690de39b13206ffdf8093d74cf9e845
Timestamp: 1715508316 Timestamp [UCT]: 2024-05-12 10:05:16 Age [y:d:h:m:s]: 00:288:21:19:08
Block: 1020346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206429 RingCT/type: yes/0
Extra: 01a5af58ca1059bac9c00d1a6cf3402f665690de39b13206ffdf8093d74cf9e84502110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33292580b6d99ba58d24e2d5fb8d1133441fae7f193499dca84f0bd663e20416 0.600000000000 1484409 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": 1020356, "vin": [ { "gen": { "height": 1020346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33292580b6d99ba58d24e2d5fb8d1133441fae7f193499dca84f0bd663e20416" } } ], "extra": [ 1, 165, 175, 88, 202, 16, 89, 186, 201, 192, 13, 26, 108, 243, 64, 47, 102, 86, 144, 222, 57, 177, 50, 6, 255, 223, 128, 147, 215, 76, 249, 232, 69, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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