Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e2afa747200b52d44024619886160d1c455c2e1300fedfcd3ddecddb0cf3088

Tx prefix hash: 97a496588611c60e4ea4845abdaef8b361d26b5b5eac3fcdfecec83d45f6cc75
Tx public key: cc542985861fed95adc33cbd7f062c2934ba1445c78f75f5d6fd984576a79e75
Timestamp: 1580602750 Timestamp [UCT]: 2020-02-02 00:19:10 Age [y:d:h:m:s]: 04:290:21:38:31
Block: 56791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1099178 RingCT/type: yes/0
Extra: 01cc542985861fed95adc33cbd7f062c2934ba1445c78f75f5d6fd984576a79e7502110000000a4ac5aa02000000000000000000

1 output(s) for total of 397.950142880000 dcy

stealth address amount amount idx
00: 38097d8af096aa4fcee76c48d9aeaa4340c037022d606f579e049a5765d136b0 397.950142880000 104724 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": 56801, "vin": [ { "gen": { "height": 56791 } } ], "vout": [ { "amount": 397950142880, "target": { "key": "38097d8af096aa4fcee76c48d9aeaa4340c037022d606f579e049a5765d136b0" } } ], "extra": [ 1, 204, 84, 41, 133, 134, 31, 237, 149, 173, 195, 60, 189, 127, 6, 44, 41, 52, 186, 20, 69, 199, 143, 117, 245, 214, 253, 152, 69, 118, 167, 158, 117, 2, 17, 0, 0, 0, 10, 74, 197, 170, 2, 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