Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a86d0dd00ff86d9203a5a3c3374cd49cd6bedd4a5a44831dfe1861973b9f3d6e

Tx prefix hash: 2a8d976d3bf0a2cba8c60692fa5fd54d75fdaa34d18ee647bec46beca1f32b4f
Tx public key: 8865d767ead33316880a5f8bf22b073d4aaaa77a289a77834a3edf97297a5944
Timestamp: 1709515800 Timestamp [UCT]: 2024-03-04 01:30:00 Age [y:d:h:m:s]: 01:249:14:54:30
Block: 970643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437123 RingCT/type: yes/0
Extra: 018865d767ead33316880a5f8bf22b073d4aaaa77a289a77834a3edf97297a594402110000000e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12cd4143a108ab5ce9f671e8cd1b243ab0f6dd1d15db3f5c9a1dc75c2deb1f52 0.600000000000 1430502 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": 970653, "vin": [ { "gen": { "height": 970643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12cd4143a108ab5ce9f671e8cd1b243ab0f6dd1d15db3f5c9a1dc75c2deb1f52" } } ], "extra": [ 1, 136, 101, 215, 103, 234, 211, 51, 22, 136, 10, 95, 139, 242, 43, 7, 61, 74, 170, 167, 122, 40, 154, 119, 131, 74, 62, 223, 151, 41, 122, 89, 68, 2, 17, 0, 0, 0, 14, 89, 218, 211, 245, 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