Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfa4fe117c7fc82a2d3f30207c7954a700b7772f6495679b9a75bbd2572415e7

Tx prefix hash: f47374146a578391c71f91e8b5772445ab17bcb65b177c6a0f764d86edd6ecb1
Tx public key: fee913a2cb4e343b5ae9a2eb4292344d45f45104df3e69aee51a2f16c8170e96
Timestamp: 1711813248 Timestamp [UCT]: 2024-03-30 15:40:48 Age [y:d:h:m:s]: 01:009:16:22:41
Block: 989707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267859 RingCT/type: yes/0
Extra: 01fee913a2cb4e343b5ae9a2eb4292344d45f45104df3e69aee51a2f16c8170e960211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10fecf41d66e9afffb9d6115e9acde4bdde89baf949e74fcf7ec151749df814d 0.600000000000 1450025 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": 989717, "vin": [ { "gen": { "height": 989707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10fecf41d66e9afffb9d6115e9acde4bdde89baf949e74fcf7ec151749df814d" } } ], "extra": [ 1, 254, 233, 19, 162, 203, 78, 52, 59, 90, 233, 162, 235, 66, 146, 52, 77, 69, 244, 81, 4, 223, 62, 105, 174, 229, 26, 47, 22, 200, 23, 14, 150, 2, 17, 0, 0, 0, 4, 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