Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6edb8b73937dfff2a1da527ebfee340cbeccbee225737ac2b038acc1c74d6155

Tx prefix hash: 330b3eae2cb8e359897a42996031e29c3b83d131fa125c42dc75dbe99ca4447e
Tx public key: 790ea5bd4b0c0c57c619da69379ebdb81052e30c6c061e211cfc92114f502f76
Timestamp: 1707840766 Timestamp [UCT]: 2024-02-13 16:12:46 Age [y:d:h:m:s]: 01:106:20:12:10
Block: 956737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337451 RingCT/type: yes/0
Extra: 01790ea5bd4b0c0c57c619da69379ebdb81052e30c6c061e211cfc92114f502f7602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f832c4256268e8f19a86b68fc2f8773ff770bab953ec850de890cde1bc0b748 0.600000000000 1416047 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": 956747, "vin": [ { "gen": { "height": 956737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f832c4256268e8f19a86b68fc2f8773ff770bab953ec850de890cde1bc0b748" } } ], "extra": [ 1, 121, 14, 165, 189, 75, 12, 12, 87, 198, 25, 218, 105, 55, 158, 189, 184, 16, 82, 227, 12, 108, 6, 30, 33, 28, 252, 146, 17, 79, 80, 47, 118, 2, 17, 0, 0, 0, 1, 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