Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c5ae847c14484aff211dd9405b57ceb1535161283c9c90cc41b56cc0e931250

Tx prefix hash: 6fc0b9c383d6fb5bafcafae779fa6bbc0c4c1052c7f60448ff17ce6bfe779c9d
Tx public key: c07cceb7fd1c48b12ceb38ce57668bbe1f22452f4d896caa2f1311f7cf2ddda9
Timestamp: 1704553877 Timestamp [UCT]: 2024-01-06 15:11:17 Age [y:d:h:m:s]: 01:308:15:55:58
Block: 929490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479433 RingCT/type: yes/0
Extra: 01c07cceb7fd1c48b12ceb38ce57668bbe1f22452f4d896caa2f1311f7cf2ddda902110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8c430837813d1700f1c37c0fdaa61ad4e390ba8489d8e179a8464055dc92e83 0.600000000000 1387366 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": 929500, "vin": [ { "gen": { "height": 929490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8c430837813d1700f1c37c0fdaa61ad4e390ba8489d8e179a8464055dc92e83" } } ], "extra": [ 1, 192, 124, 206, 183, 253, 28, 72, 177, 44, 235, 56, 206, 87, 102, 139, 190, 31, 34, 69, 47, 77, 137, 108, 170, 47, 19, 17, 247, 207, 45, 221, 169, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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