Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 249bf1165824cab57827c8ae9ceef34a37c9c34fce7865a56e569a8c6c0baf30

Tx prefix hash: 869f171d979309fb440ae16f40d4e648e4a199197c6f1de361cc7c317ad3595b
Tx public key: 0a978a4dd08d377ed05f617d4d512937a929fa292ea3c5de88443c12dc85e059
Timestamp: 1705624131 Timestamp [UCT]: 2024-01-19 00:28:51 Age [y:d:h:m:s]: 01:299:23:11:16
Block: 938355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473205 RingCT/type: yes/0
Extra: 010a978a4dd08d377ed05f617d4d512937a929fa292ea3c5de88443c12dc85e0590211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4356521f8bae2808e967cd7c4a296d6efc913674a0559e20e8f7a89b786f178 0.600000000000 1396425 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": 938365, "vin": [ { "gen": { "height": 938355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4356521f8bae2808e967cd7c4a296d6efc913674a0559e20e8f7a89b786f178" } } ], "extra": [ 1, 10, 151, 138, 77, 208, 141, 55, 126, 208, 95, 97, 125, 77, 81, 41, 55, 169, 41, 250, 41, 46, 163, 197, 222, 136, 68, 60, 18, 220, 133, 224, 89, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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