Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7db7761ed3ad3dd851137fd705c8ee0c39a1967159593497869de8c4cf54ee4

Tx prefix hash: b6338ae70a24c2a80d7f5024c23b48eb95124351b6747f006135323744256515
Tx public key: 1c46199a6d162383db5fb70d43aee6ac71bd2ae1a3c71dd0768bc6997c28a2a6
Timestamp: 1709130007 Timestamp [UCT]: 2024-02-28 14:20:07 Age [y:d:h:m:s]: 01:050:03:39:49
Block: 967441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296864 RingCT/type: yes/0
Extra: 011c46199a6d162383db5fb70d43aee6ac71bd2ae1a3c71dd0768bc6997c28a2a602110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76bbcd6e6fa8c78b852df99947a9e30b3f5425b6d05d067281fea6fd35d1aad1 0.600000000000 1427220 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": 967451, "vin": [ { "gen": { "height": 967441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76bbcd6e6fa8c78b852df99947a9e30b3f5425b6d05d067281fea6fd35d1aad1" } } ], "extra": [ 1, 28, 70, 25, 154, 109, 22, 35, 131, 219, 95, 183, 13, 67, 174, 230, 172, 113, 189, 42, 225, 163, 199, 29, 208, 118, 139, 198, 153, 124, 40, 162, 166, 2, 17, 0, 0, 0, 5, 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