Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c52648c18772ce6f1be1ae6cfb9bebe32ebcf4ca6ba67e9a2cabb715842822d

Tx prefix hash: 6e8dd6bc77bbec9d2122ed99dbac4d60bd24e19fd4f82a4ab47e5117629a4f91
Tx public key: a48326296a02d6e91a41715cfd4f360d80c460a89a5072b6a77f97e70122b9fd
Timestamp: 1734725596 Timestamp [UCT]: 2024-12-20 20:13:16 Age [y:d:h:m:s]: 00:015:10:21:00
Block: 1179546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11022 RingCT/type: yes/0
Extra: 01a48326296a02d6e91a41715cfd4f360d80c460a89a5072b6a77f97e70122b9fd0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a71e5edc9edc7cabf3306f67078aca11bde6cd83348e400a8d0cc7fd7f4b143b 0.600000000000 1665941 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": 1179556, "vin": [ { "gen": { "height": 1179546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a71e5edc9edc7cabf3306f67078aca11bde6cd83348e400a8d0cc7fd7f4b143b" } } ], "extra": [ 1, 164, 131, 38, 41, 106, 2, 214, 233, 26, 65, 113, 92, 253, 79, 54, 13, 128, 196, 96, 168, 154, 80, 114, 182, 167, 127, 151, 231, 1, 34, 185, 253, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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