Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74f3cd3b3166f40b5e932a94d66445fbeabb3c9356d9246c7f8f93e1995f09fc

Tx prefix hash: ca258dcf19444369834ac655b118d7f5fdc01d339e182d1cebeaf190ddf2d053
Tx public key: 0fc304bb522048419c9dbc65107585ad9b661c2422f7f926dc9e46c7b3b75401
Timestamp: 1731481442 Timestamp [UCT]: 2024-11-13 07:04:02 Age [y:d:h:m:s]: 00:216:12:18:09
Block: 1152641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154509 RingCT/type: yes/0
Extra: 010fc304bb522048419c9dbc65107585ad9b661c2422f7f926dc9e46c7b3b754010211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1d20ab2d6b5c1d7d78fab6498d0704b341a036060ef87a38d0ea3dec6e696c9 0.600000000000 1638244 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": 1152651, "vin": [ { "gen": { "height": 1152641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1d20ab2d6b5c1d7d78fab6498d0704b341a036060ef87a38d0ea3dec6e696c9" } } ], "extra": [ 1, 15, 195, 4, 187, 82, 32, 72, 65, 156, 157, 188, 101, 16, 117, 133, 173, 155, 102, 28, 36, 34, 247, 249, 38, 220, 158, 70, 199, 179, 183, 84, 1, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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