Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6a1fd6e6debf0a6770c23bd763a6ec31a198ff84dd47d21569996e6cb4060ec

Tx prefix hash: ec9d36e17d43fe29827c6bda864f33fcf9271956c7e4e48c3d2b0eb998972bc5
Tx public key: a001438ecb72e169307f30232581e6aa3cb5e160a0a57f4a2d7a8b671676dedf
Timestamp: 1736049953 Timestamp [UCT]: 2025-01-05 04:05:53 Age [y:d:h:m:s]: 00:160:15:41:10
Block: 1190488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114557 RingCT/type: yes/0
Extra: 01a001438ecb72e169307f30232581e6aa3cb5e160a0a57f4a2d7a8b671676dedf021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abb3284e59f1ecdd96cee25b944c1070c6172e79071971df9479d75018dfee43 0.600000000000 1677005 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": 1190498, "vin": [ { "gen": { "height": 1190488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abb3284e59f1ecdd96cee25b944c1070c6172e79071971df9479d75018dfee43" } } ], "extra": [ 1, 160, 1, 67, 142, 203, 114, 225, 105, 48, 127, 48, 35, 37, 129, 230, 170, 60, 181, 225, 96, 160, 165, 127, 74, 45, 122, 139, 103, 22, 118, 222, 223, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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