Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69a46f33059ce842c940a84fe427e4afb263ba46b76391159863a3f73fb27712

Tx prefix hash: 32f4a0f99f563d16a69a226d9adff21401ee03f6c0217f3ac664e73378b89ecb
Tx public key: c4e01b84bc1e8b21d8bf54ce20a33cf8d29642e6e7ccdd2b79fce201047d81a9
Timestamp: 1731770989 Timestamp [UCT]: 2024-11-16 15:29:49 Age [y:d:h:m:s]: 00:215:05:08:41
Block: 1155040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153552 RingCT/type: yes/0
Extra: 01c4e01b84bc1e8b21d8bf54ce20a33cf8d29642e6e7ccdd2b79fce201047d81a90211000000111f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8d8085ca92199c0b7ecbe3d426f48178abd7a5180ecb9ea1a7489e77324da09 0.600000000000 1640653 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": 1155050, "vin": [ { "gen": { "height": 1155040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8d8085ca92199c0b7ecbe3d426f48178abd7a5180ecb9ea1a7489e77324da09" } } ], "extra": [ 1, 196, 224, 27, 132, 188, 30, 139, 33, 216, 191, 84, 206, 32, 163, 60, 248, 210, 150, 66, 230, 231, 204, 221, 43, 121, 252, 226, 1, 4, 125, 129, 169, 2, 17, 0, 0, 0, 17, 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