Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05d25ce240cbf270182363f467575a6ab158c4432d11a9724909df8ba4aed7af

Tx prefix hash: 990478936238efe4b4aa5bf018d4aa958e9a7aa867799d482e62e4b472d92a62
Tx public key: 027b2134ea85dd4108823e2cac982d4128b187c890baa89c65d03c37b60da83f
Timestamp: 1719100216 Timestamp [UCT]: 2024-06-22 23:50:16 Age [y:d:h:m:s]: 00:306:23:46:03
Block: 1050076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219381 RingCT/type: yes/0
Extra: 01027b2134ea85dd4108823e2cac982d4128b187c890baa89c65d03c37b60da83f021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dc7939576f781801c22dc5aa591a8cff928b3517f96187ed95ab9316ff8a8f3 0.600000000000 1520231 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": 1050086, "vin": [ { "gen": { "height": 1050076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dc7939576f781801c22dc5aa591a8cff928b3517f96187ed95ab9316ff8a8f3" } } ], "extra": [ 1, 2, 123, 33, 52, 234, 133, 221, 65, 8, 130, 62, 44, 172, 152, 45, 65, 40, 177, 135, 200, 144, 186, 168, 156, 101, 208, 60, 55, 182, 13, 168, 63, 2, 17, 0, 0, 0, 2, 215, 73, 245, 17, 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