Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66e7ff0abcb91938f5ab9fe9122c4075edce6939349f1a321e4a909e9a9c8cb1

Tx prefix hash: 6a164059a8dd04aee61e6f13a19955b93fe51657128d636fe3f03c0c0e99d43d
Tx public key: a6423eec5acf3231b8d22812f11414e927a36d45cb773858cf42b8f8fe92ef13
Timestamp: 1721341819 Timestamp [UCT]: 2024-07-18 22:30:19 Age [y:d:h:m:s]: 00:246:01:00:28
Block: 1068693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175746 RingCT/type: yes/0
Extra: 01a6423eec5acf3231b8d22812f11414e927a36d45cb773858cf42b8f8fe92ef1302110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aad6d807c373090d7f5d00a7c9340b7e32089159d2c6bae3ea37765fcd4025bb 0.600000000000 1539822 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": 1068703, "vin": [ { "gen": { "height": 1068693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aad6d807c373090d7f5d00a7c9340b7e32089159d2c6bae3ea37765fcd4025bb" } } ], "extra": [ 1, 166, 66, 62, 236, 90, 207, 50, 49, 184, 210, 40, 18, 241, 20, 20, 233, 39, 163, 109, 69, 203, 119, 56, 88, 207, 66, 184, 248, 254, 146, 239, 19, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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