Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59cb694be48db066a1dd7d64d941dd2e5e141d056032500efefcf3a555e370b5

Tx prefix hash: 12fe6e88c6207e6298c3574c4d43721c9cb905e014677991d1f99efe617321f9
Tx public key: a82a0ae9c21a0533bd8fc185ef869fce405225503c572d5b57ab161a5c5494dc
Timestamp: 1709038313 Timestamp [UCT]: 2024-02-27 12:51:53 Age [y:d:h:m:s]: 01:086:20:57:40
Block: 966687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323134 RingCT/type: yes/0
Extra: 01a82a0ae9c21a0533bd8fc185ef869fce405225503c572d5b57ab161a5c5494dc0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600150000000 dcy

stealth address amount amount idx
00: 1b685e9c85609b9f87521b4b9618920bd630c66b7d2adbb30d9927d4f882941c 0.600150000000 1426456 of 0

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": 966697, "vin": [ { "gen": { "height": 966687 } } ], "vout": [ { "amount": 600150000, "target": { "key": "1b685e9c85609b9f87521b4b9618920bd630c66b7d2adbb30d9927d4f882941c" } } ], "extra": [ 1, 168, 42, 10, 233, 194, 26, 5, 51, 189, 143, 193, 133, 239, 134, 159, 206, 64, 82, 37, 80, 60, 87, 45, 91, 87, 171, 22, 26, 92, 84, 148, 220, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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