Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 713cd6f8d16d5254d5a3f4da1288c55257611461145aa95e8c09670f21098bc6

Tx prefix hash: 33ae7b5b9eac1f515cebd42ea90ca9a0d48e5f91c24727e319b5e71659288952
Tx public key: cb8c106c3092540e14d4fe760fc8623cce74d992041a98e0f4b4e6550045bc41
Timestamp: 1705180326 Timestamp [UCT]: 2024-01-13 21:12:06 Age [y:d:h:m:s]: 01:086:14:06:35
Block: 934675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322995 RingCT/type: yes/0
Extra: 01cb8c106c3092540e14d4fe760fc8623cce74d992041a98e0f4b4e6550045bc410211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3e5d8c0278fdf20fff14707637f93f734ef9e520d7d3f0ae7d6e8dddda78366 0.600000000000 1392689 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": 934685, "vin": [ { "gen": { "height": 934675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3e5d8c0278fdf20fff14707637f93f734ef9e520d7d3f0ae7d6e8dddda78366" } } ], "extra": [ 1, 203, 140, 16, 108, 48, 146, 84, 14, 20, 212, 254, 118, 15, 200, 98, 60, 206, 116, 217, 146, 4, 26, 152, 224, 244, 180, 230, 85, 0, 69, 188, 65, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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