Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43cf69d240270fcfacb62501c6f2fd098cbc240448112899ed723861645dd28f

Tx prefix hash: 953c5647cbf3f4c7bc30d46aec81a81ddaf0d42b42b75bf420a383df98f71c98
Tx public key: c73fb20d347aa1808d83a2a3481b39ad2186e0d7c17e83df15a62fe740e5476a
Timestamp: 1625658533 Timestamp [UCT]: 2021-07-07 11:48:53 Age [y:d:h:m:s]: 04:134:17:18:06
Block: 289696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124892 RingCT/type: yes/0
Extra: 01c73fb20d347aa1808d83a2a3481b39ad2186e0d7c17e83df15a62fe740e5476a0211000000724b22f71d000000000000000000

1 output(s) for total of 67.315860081000 dcy

stealth address amount amount idx
00: 61dd457c36f0b671a7be579b0a03b01732a82417e1715864e606764c0c891588 67.315860081000 606808 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": 289706, "vin": [ { "gen": { "height": 289696 } } ], "vout": [ { "amount": 67315860081, "target": { "key": "61dd457c36f0b671a7be579b0a03b01732a82417e1715864e606764c0c891588" } } ], "extra": [ 1, 199, 63, 178, 13, 52, 122, 161, 128, 141, 131, 162, 163, 72, 27, 57, 173, 33, 134, 224, 215, 193, 126, 131, 223, 21, 166, 47, 231, 64, 229, 71, 106, 2, 17, 0, 0, 0, 114, 75, 34, 247, 29, 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